After having set up the conf/configuration.xml file as described in the Portal Extension section you can proceed with customizing of Groovy templates of portlets.

This section mentions code from Portal Extension Example from the GateIn Portal Quickstarts collection.

Since we do not like the text and layout used in the default HomePagePortlet that comes with out-of-the-box GateIn Portal installation, we want to change it in our Extension. All we need to do is to copy the file

 
portal.war/templates/groovy/webui/component/UIHomePagePortlet.gtmpl 

from gatein.ear into our Extension project where it needs to be placed under the analogous path, in our case under

 
war/src/main/webapp/templates/groovy/webui/component/UIHomePagePortlet.gtmpl 

After adapting the copied file to our needs and deploying the Extension EAR, the HomePagePortlet mirrors the changes we have done.

Note that shadowing of built-in Groovy templates is controlled by the order of <dependencies> in the configuration of the Portal Container (or Extension) as described in the previous section. Namely, when a template with the same path, say /dir/subdir/template.gtmpl, is available in more than one of the dependencies, the one from the context closest to the end of the list of dependencies is chosen. To ensure that the template available in gatein-portal-extension will be chosen, we have added gatein-portal-extension as the last element of the list.